|
•
|
Route Access Lists – The basic building block of a routing policy. Route access lists filter routes based on a range of IP addresses.
|
|
•
|
IP Prefix Lists – A more advanced element of a routing policy. An IP Prefix list filters routes based on IP prefixes.
|
|
•
|
AS Path Access Lists – A basic building block used for Border Gateway Protocol (BGP) routing. These lists filter Autonomous System (AS) paths.
|
|
•
|
Route Maps – Route-maps provide detailed control over routes during route selection or route advertisement by a routing protocol, and in route redistribution between routing protocols. For this level of control you use IP Prefix Lists, Route Access Lists and AS Path Access Lists to specify IP addresses, address ranges, and Autonomous System paths.
|
context <context_name>
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
route-access-list standard <identifier> { permit | deny ) { <ip_address> <wildcard_mask> | any |<network_address> }
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
|
•
|
Use the match and set commands in Route Map Configuration mode to configure the route map. Refer to the Command Line Interface Reference for more information on these commands.
|
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
To add static routes to a context configuration, you must know the names of the interfaces that are configured in the current context. Use the show ip interface command to list the interfaces in the current context (Exec mode).
context <context_name>
ip route { <ip_address> [ <ip_mask> ] | <ip_addr_mask_combo> } { next-hop <next_hop_address> | <egress_name> [ precedence <precedence> [ cost <cost> ]
You can configure a maximum of 1,200 static routes per context. Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
context context_name
no ip route { <ip_address> <ip_mask> | <ip_addr_mask_combo> } <next_hop_address> <egress_name> [ precedence <precedence> ] [ cost <cost> ]
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
Important: During system task recovery, it is possible for a dynamically-learned forwarding entry to incorrectly remain in the system forwarding table if that forwarding entry has been removed from the dynamic routing protocol during the recovery.OSPF uses a link-state algorithm to build and calculate the shortest path to all known destinations.
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter in this guide.
|
Important: The default cost for OSPF on the system is 10. To change the cost, refer to the ip ospf cost command in the Ethernet Interface Configuration Commands section of the Command Line Interface Reference.|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
To confirm the OSPF router configuration, use the following command and look for the section labeled router ospf in the screen output:
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter in this guide.
|
area { area_id | area_ip_address } [ default-cost dflt-cost ] [ stub stub-area ] [ virtual-link vl-neighbor-ipv4address ]
Important: The default cost for OSPFv3 on the system is 10. To change the cost, refer to the ipv6 ospf cost command in the Ethernet Interface Configuration Commands section of the Command Line Interface Reference.|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
To confirm the OSPF router configuration, use the following command and look for the section labeled router ipv6 ospf in the screen output:
|
•
|
show ip route: Displays information for all types of routes in the current contexts routing table.
|
|
•
|
show ip static-route: Displays information only for static routes in the current contexts routing table.
|
|
•
|
show ip ospf: Displays OSPF process summary information in the current context.
|
|
•
|
show ipv6 ospf: Displays OSPFv3 process summary information in the current context.
|
This example shows sample output of the command, show ip route.
|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter in this guide.
|
Mobile devices communicate to the Internet through Home Agents (HAs). HAs assign IP addresses to the mobile node from a configured pool of addresses. These addresses are also advertised to Internet routers through an IP routing protocol to ensure dynamic routing. The BGP-4 protocol is used as a monitoring mechanism between an HA and Internet router with routing to support Interchassis Session Recovery (ICSR). (Refer to the Interchassis Session Recovery appendix in this guide for more information.)
|
•
|
Through BGP Configuration Mode redistribution commands, all or some of the connected routes are redistributed into the BGP domain. (IP pool and loopback routes are present in the IP routing table as connected routes.) The network routemap command provides the flexibility to change many BGP attributes.
|
|
•
|
Through the BGP Configuration Mode network commands, connected routes are explicitly configured for advertisement into the BGP domain. The network routemap command provides the flexibility to change many BGP attributes. Refer to the Border Gateway Protocol Configuration Mode Commands section of the Command Line Interface Reference for details on these commands.
|
Important: If a BGP task restarts because of a processing card failure, a migration, a crash, or the removal of a processing card, all peering session and route information is lost.|
•
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.
|
redistribute bgp { bgp | connected | static } [ metric <metric_value> ] [ metric-type { 1 | 2 } ] [ route-map <route_map_name> ]
|
•
|
The redistribution options are connected, ospf, rip, or static. Refer to the Border Gateway Protocol Configuration Mode Commands section of the Command Line Interface Reference for details on the redistribute command.
|
|
•
|
Save your configuration as described in Verifying and Saving Your Configuration chapter of this guide.
|
When Echo is active, a stream of Echo packets is sent to the other endpoint which then forwards these back to the sender. Echo can be globally enabled via the bfd-protocol command, and/or individually enabled/disabled per interface. This function is used to test the forwarding path on the remote system.
This section describes how to configure and enable basic BFD routing protocol support in the system.
Enable BFD on a BGP Neighbor. See Associate BGP Neighbors with the Context for additional information.
Enable BFD on a BGP Neighbor. See Associate BGP Neighbors with the Context for additional information.
Configure an active BFD session using one of the above methods and use same BFD neighbor while configuring the active interface. See Associate BFD Neighbor Groups with the BFD Protocol for additional information.
Important: Save your configuration as described in the Verifying and Saving Your Configuration chapter of this guide.